fix(geo): ensure the store contains map before bind to stores list #1582
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aziz-access
added
the
bug
alecarn
requested changes
Jan 17, 2024
| @@ -26,6 +26,9 @@ export class FeatureStoreInMapResolutionStrategy extends EntityStoreStrategy { | |||
| * @param store Feature store | |||
| */ | |||
| bindStore(store: FeatureStore) { | |||
| if (!store && !store.layer && !store.layer.map) { | |||
| return; | |||
| } | |||
There was a problem hiding this comment.
On semble simplement ignorer l'erreur plutot que de la corriger. Quel est la source du problème?
There was a problem hiding this comment.
Je n'arrive pas à comprendre exactement la source du problème, car je n'ai pas suffisamment d'informations. donc j'ai ignorer l'erreur.
la seule chose que je comprends c'est que la valeur du store parfois undefined
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the current behavior? (You can also link to an open issue here)
this behavier reated to #1567
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information: